Adding a note about not using configured component templates from API-created index templates #8457
Conversation
…-created index templates
kvalliyurnatt
added
exclude-from-release-notes
kvalliyurnatt
requested review from
barkbay,
kvalliyurnatt,
naemono,
pebrc and
rhr323
|
I am unable to find the updated documentation as per this PR. Am I missing something ? 🤔 @masseyke Would you mind confirming, where this PR got merged and released ? |
|
This note was removed a month later by this change: #8496. I'm still trying to figure out where the documentation went. |
|
@masseyke : After the migration to the new docs V3 system, the majority of ECK docs have been moved to Some other docs (reference documentation, release notes, etc) are still in cloud-on-k8s repo, but in markdown format and not in asciidoc anymore. The legacy asciidoc docs are still in this repo but only in the old So, answering your question:
I'm very sorry if we missed this message while migrating the docs! For some reason I cannot even see the note in the |
Bringing in a change lost during docs migration: elastic/cloud-on-k8s#8457 @masseyke , I've reworded a bit the note, feel free to review and share your thoughts!
Bringing back a change we've lost during migration: #8457
|
@akashsingh-aps , this is a very good finding. Next time don't hesitate pinging us directly in the internal docs slack channel, or opening a new issue in docs-content asking about the missing content ;) I've created elastic/docs-content#2823 to fix the issue in the new docs. And also #8815 to add the note in 2.16 docs. |
…cies (#2823) Bringing in a change lost during docs migration: elastic/cloud-on-k8s#8457 @masseyke , I've reworded a bit the note, feel free to review and share your thoughts!
Bringing back a change we've lost during migration: #8457
5 participants
Right now, Elasticsearch does not allow you to pull a component template created in a configuration policy into an index template created through the API. This has the potential to be dangerous to users, so I'm adding a note to the documentation. This will hopefully be fixed in elastic/elasticsearch#118594, and at that point we can change this note to only refer to versions before that one.